fix: optimize CAN receive timeout timing with perf_counter - #2089
fix: optimize CAN receive timeout timing with perf_counter#2089luojiaaoo wants to merge 5 commits into
Conversation
|
Tick the box to add this pull request to the merge queue (same as
|
fallenmi
left a comment
fallenmi
left a comment
There was a problem hiding this comment.
Please keep the Coveralls action pinned to a full commit SHA. On exact base b4f82ab, all 9 external Actions references are full-SHA pinned; exact head 0cd6639 changes both Coveralls uses to the mutable v2.3.8 tag, making these the only two mutable refs. Moving that tag would change third-party code executed with the workflow token without a reviewed repository diff. v2.3.8 currently resolves to 8d6379e14d29928660c4ba802d8e85393440b329, so please pin that SHA with a version comment (or retain the prior pin). I separately exercised the timeout loop on the exact base and head; both exit correctly, and the live upstream checks are green.
Reviewed with OpenAI Codex.
2 participants
Description
Replace
time.time()withtime.perf_counter()for CAN receive timeout calculations.perf_counter()is better suited for measuring elapsed time and avoids issues caused by system clock adjustments, while also providing better timing precision for the receive loop.